home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
os2
/
sfutils.zip
/
SFUTILS.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1997-04-29
|
27KB
|
786 lines
ΓòÉΓòÉΓòÉ 1. SFUtils description ΓòÉΓòÉΓòÉ
SFUtils (Startup Folder Utilities) consists of two utilities, ObjWait and
AppWait, and a helper utility for ObjWait, MakeObj.
AppWait and ObjWait have the same purpose--to allow applications stored on a
network drive to be run by the OS/2 startup folder at bootup. Until the network
drives are available, they display a dialog box that indicates, "Waiting for
x:".
The two "Wait" utilities take different approaches to solving this problem, and
have different strengths and weaknesses. They are described in their own
sections and there is a chart that compares their features.
ObjWait
AppWait
SFUtils may be purchased for personal or site use. Please see Licensing
information.
Installation
ΓòÉΓòÉΓòÉ 2. ObjWait and AppWait features ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFeature ΓöéObjWait ΓöéAppWait Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProgram objects required Γöé2 Γöé1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéObject Id required ΓöéY ΓöéN Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéNumber of drives that can be waited for Γöé24 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCan start OS/2, DOS, Win, bat, and cmd ΓöéY ΓöéY Γöé
Γöésessions Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCan choose specific DOS/Win settings ΓöéY ΓöéN Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCan choose program session type ΓöéY ΓöéN Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéApplication object is hatched while app runs ΓöéY ΓöéY Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéApplication object is hatched while waiting ΓöéN ΓöéY Γöé
Γöéfor network drives Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéObject in startup folder remains hatched ΓöéN ΓöéY Γöé
Γöéwhile app runs Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDouble clicking object brings program to ΓöéY ΓöéY Γöé
Γöéforeground Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 3. Installation ΓòÉΓòÉΓòÉ
Place the distribution files in any directory on a local hard drive. They don't
have to be in a directory in your path as long as you specify the full path
when you set up your applications.
No changes to config.sys are necessary, and there are no workplace shell
classes to register.
For the MakeObj help to function, MakeObj must be run from the directory where
the help file is stored. Alternately, you can put the help file in a directory
listed in the HELP= line of config.sys.
ΓòÉΓòÉΓòÉ 4. ObjWait ΓòÉΓòÉΓòÉ
ObjWait takes as parameters the drive letters you want to wait for, and the
object id of a Workplace Shell object you want to open. ObjWait waits for each
drive letter to be available, and then opens the object you specified.
With ObjWait, you will need at least two program objects. One program object
will be for ObjWait itself, and will go in the startup folder. The other
program object will be for the application you want to run. If the ObjWait
object is double clicked, it checks for the specified drives (as many as you
specify) and then opens the specified application object. The ObjWait icon will
not remain hatched while the application is running. Double clicking the
ObjWait object again will bring the application to the foreground.
ObjWait works equally well with any type of program object including OS/2, DOS,
or Windows programs. You can set specific session options and DOS settings and
they will all be honored just as if you had opened the object directly.
Before you can use ObjWait, you must usually create a new application program
object that has a specific object id. MakeObj makes this easy to do, and a Rexx
sample is included that can be modified to automate the process.
ObjWait quick start
ObjWait tutorial
ObjWait advanced topics
Feature chart
AppWait
ΓòÉΓòÉΓòÉ 4.1. ObjWait quick start ΓòÉΓòÉΓòÉ
Run MakeObj and follow the online help to create a startup object and an
application object. Complete the settings of the application icon so it starts
your application.
Reboot your system and logon to the network and your application will start.
For more detailed information, please see the ObjWait tutorial and ObjWait
advanced topics.
ΓòÉΓòÉΓòÉ 4.2. ObjWait tutorial ΓòÉΓòÉΓòÉ
There are usually two steps you will take to setup ObjWait to start an
application.
1. Create two new icons using MakeObj (one for the startup folder and a new
application icon).
2. Edit the new application object to have the correct settings to run your
application.
That's it. Now you can reboot and logon to the network, your applications
should start.
For more information on ObjWait see Advanced topics
ΓòÉΓòÉΓòÉ 4.2.1. Using MakObj ΓòÉΓòÉΓòÉ
MakeObj creates a startup object and an application object with an object id.
It is one of the utilities in SFUtils.
Run MakeObj and fill in the required fields. Online help is available.
1. Enter a name for your application object
2. Enter an object id.
Note: All object id's must be unique so you might want to use your
initials or some other unusual identifier as part of the id. Also, the id
must begin with < and end with >
3. Enter the full path to ObjWait.
4. Choose the network drive letters you want to wait for by clicking on
them.
5. Press create and one icon will appear on your desktop and one will be
added to your startup folder.
Errors are usually caused by one of two problems. An object id that is not
unique, or an appliction name that is not unique on the desktop. Try again
with different names.
Once the icons are successfully created, you can exit MakeObj and go onto the
next step.
ΓòÉΓòÉΓòÉ 4.2.2. Application object ΓòÉΓòÉΓòÉ
The next step is to edit the settings of the new object you created so that it
starts your application.
MakeObj will open the settings notebook for the new object, and you can open
the settings notebook for your original application.
OS/2 program settings
For OS/2 programs, you need only copy the info from the three fields on the
"Program" page. This can easily be done using OS/2's copy and paste features.
DOS and Windows settings
For DOS and Windows Applications you need to copy the DOS settings in addition
to the program page as discussed for OS/2 programs.
If you are running OS/2 Warp you can use the Print (to file) option from the
DOS Settings window to save all the settings from the old object into a
temporary file. You can then use the Load option from the DOS Settings window
of the new object.
If you have OS/2 v2 you will need to manually copy the DOS settings. You can
change to the settings page and open the DOS settings window of the new and old
objects. Then change each setting in the new object to be the same as the
setting in the old object.
Once your application object is setup correctly you can reboot and see ObjWait
in action.
ΓòÉΓòÉΓòÉ 4.3. ObjWait advanced topics ΓòÉΓòÉΓòÉ
Using your existing application object
If you have utilities (not supplied with SFUtils) that can determine an
object's id, or set an id for an existing object, you don't need to run
MakeObj. You can instead manually create an object to be put in in the startup
folder. This startup object should have objwait.exe as the program name; the
drive letters you want to wait for as the first parameter; and the object id as
the second parameter. (See useage below).
The author is aware of Object Utility/2 (supplied with Visual Age C++) that can
determine the id of an object. (Note that many objects don't have id's.) The
author is also aware of Deskman/2 (from Devtech) that allows you to determine
object id's and assign object id's.
Starting file objects with ObjWait
ObjWait can start file objects in addition to program objects. File objects are
the objects the workplace shell displays in the drives folder for your
executable files. To start these objects, simply list the full path to the file
object as the second parameter to ObjWait (and don't use < and >).
Creating objects with REXX
A command file SMakeObj.cmd is included that prompts for input and then creates
program objects. You can modify this sample to automate the process of setting
up ObjWait to start applications.
ObjWait Useage (parameters)
OBJWAIT DRIVE_LETTERS OBJECTID
The following example waits for drives F: G: H: and Q: and then starts the
object that has the id <MY_OBJECT>:
ObjWait FGHQ <MY_OBJECT>
ΓòÉΓòÉΓòÉ 5. AppWait ΓòÉΓòÉΓòÉ
AppWait takes as parameters an application filename, a working directory, and
the parameters you want to pass to the application. AppWait waits for the drive
letters referenced in the filename and directory to be available, then the
AppWait screen disappears and the application is started.
AppWait uses only one program object. You can use the original object or a
shadow in your startup folder. The program icon will have hash marks while the
program is running. Double clicking on the running object will bring the
application to the foreground.
AppWait works very well for OS/2 programs and OS/2 command files. It can also
be used with DOS programs, DOS batch files, and Windows programs, but you
cannot choose any special DOS settings or set the session type.
You cannot specify additional drive letters. AppWait only waits for the drive
the executable is on and the drive the working directory is on.
AppWait.exe is very similar in operation to Linkup.exe provided with Warp
Connect. Linkup waits for a TCP/IP connection, and AppWait waits for network
drives.
AppWait quick start
AppWait tutorial
AppWait examples
AppWait formal useage syntax
Feature chart
ObjWait
ΓòÉΓòÉΓòÉ 5.1. AppWait quick start ΓòÉΓòÉΓòÉ
Modify or create a program object.
1. The Path and file name field should be the full path to AppWait.exe.
2. The Parameters field should contain the following parameters in the
following order.
a. Full path to the app you want to start.
b. Full working directory for your app.
c. Parameters to pass to your app (0 or more).
3. The program object's working directory is ignored and can be left blank.
For more detailed information, see the following:
AppWait tutorial
AppWait examples
AppWait useage syntax
ΓòÉΓòÉΓòÉ 5.2. AppWait tutorial ΓòÉΓòÉΓòÉ
The following are step by step instructions to set up a program object with
AppWait:
1. Create a new program object
You can drag a program object off the Program template in the templates
folder
You can click on a program object and type create another.
Or, you can modify a program object you already have for your app.
2. On the program page of the object, fill in the path and file name field
with AppWait.exe
If you haven't installed AppWait to a directory on your path, you must
enter the full path name. (For instance, if you have Appwait in
c:\utilities, enter c:\utilities\appwait.exe)
3. In the parameters field, supply information about your app.
For OS/2 or DOS EXE
For OS2 CMD files
For DOS BAT files
For Windows EXE
4. The working directory field of the AppWait object can be left blank. It
is overidden by the working directory passed to appwait.
5. Set the icon for the program object.
This can be done in several ways. Here is one method.
Now you can reboot and see AppWait in action.
ΓòÉΓòÉΓòÉ 5.2.1. Starting OS/2 or DOS EXE ΓòÉΓòÉΓòÉ
For OS/2 or DOS executables, pass AppWait the following parameters. Note that
the parameters must be in the correct order.
1. Full path to the executable
2. Full path of the working directory
3. Parameters for your app
Example (OS/2)
Example (DOS)
Useage syntax
ΓòÉΓòÉΓòÉ 5.2.2. Starting OS2 CMD files ΓòÉΓòÉΓòÉ
For OS/2 CMD files, pass AppWait the following parameters. Note that the
parameters must be in the correct order.
1. cmd.exe
2. Full path of the working directory
3. /cFILENAME.CMD where FILENAME.CMD is the name of your command file. (You
can include the path if needed.)
4. Parameters for your command file.
Example
Useage syntax
ΓòÉΓòÉΓòÉ 5.2.3. Starting DOS BAT files ΓòÉΓòÉΓòÉ
For DOS BAT files, pass AppWait the following parameters. Note that the
parameters must be in the correct order.
1. command.com
2. Full path of the working directory
3. /cFILENAME.BAT where FILENAME.BAT is the name of your batch file. (You
can include the path if needed.)
4. Parameters for your batch file.
Example
Useage syntax
ΓòÉΓòÉΓòÉ 5.2.4. Starting Windows EXE ΓòÉΓòÉΓòÉ
For Windows EXE, pass AppWait the following parameters. Note that the
parameters must be in the correct order.
1. winos2.com (try win.com if this doesn't work)
2. Full path of the working directory
3. The executable name. (You can include the path if needed.)
4. Parameters for the windows app.
Example
Useage syntax
ΓòÉΓòÉΓòÉ 5.2.5. Setting the icon ΓòÉΓòÉΓòÉ
Open the settings of an object that has the correct icon.
1. Change to the general page.
2. Press the edit button and the icon editor should open.
3. Choose File Save, and enter a temporary name.
4. Use the drives object to open the folder where you temporarily saved the
icon.
5. Change to the general page of the AppWait object you are creating, and
drag and drop the icon from the folder onto the icon area of the general
page.
ΓòÉΓòÉΓòÉ 5.3. AppWait examples ΓòÉΓòÉΓòÉ
See the following for examples of using AppWait.
In each example, it is assumed AppWait.exe is in the c:\util directory, and the
c:\util directory is not in the path.
For OS/2 EXE
For DOS EXE
For OS2 CMD files
For DOS BAT files
For Windows EXE
ΓòÉΓòÉΓòÉ 5.3.1. Example for OS/2 or DOS EXE ΓòÉΓòÉΓòÉ
A program object with the following settings will start Describe from the h:
drive with a default directory of c:\describe. The file name
c:\describe\data\todo will be passed as a parameter.
Path and file name:
c:\util\appwait.exe
Parameters:
h:\describe\describe.exe c:\describe c:\describe\data\todo
Working directory:
Useage syntax
ΓòÉΓòÉΓòÉ 5.3.2. Example for DOS EXE ΓòÉΓòÉΓòÉ
A program object with the following settings will start Wordperfect from the h:
drive with a default directory of h:\wpData, and the file name h:\WpData\todo
will be passed as a parameter.
Path and file name:
c:\util\appwait.exe
Parameters:
h:\wp51\wp.exe h:\wpData h:\WpData\todo
Working directory:
Useage syntax
ΓòÉΓòÉΓòÉ 5.3.3. Example for CMD ΓòÉΓòÉΓòÉ
A program object with the following settings will run the command file
copyNew.cmd with a working directory of f:\newfiles, and pass c:\latest as a
parameter.
Path and file name:
c:\util\appwait.exe
Parameters:
cmd.exe f:\newfiles /ccopyNew.cmd c:\latest
Working directory:
Useage syntax
ΓòÉΓòÉΓòÉ 5.3.4. Example for BAT ΓòÉΓòÉΓòÉ
A program object with the following settings will run the batch file
copyNew.bat with a working directory of f:\newfiles, and pass c:\latest as a
parameter.
Path and file name:
c:\util\appwait.exe
Parameters:
command.com f:\newfiles /ccopyNew.bat c:\latest
Working directory:
Useage syntax
ΓòÉΓòÉΓòÉ 5.3.5. Example for Windows EXE ΓòÉΓòÉΓòÉ
A program object with the following settings will run America Online with a
working directory of m:\aol30.
Path and file name:
c:\util\appwait.exe
Parameters:
winos2.com m:\aol30\aol.exe m:\aol30
Working directory:
Useage syntax
ΓòÉΓòÉΓòÉ 5.4. AppWait useage syntax ΓòÉΓòÉΓòÉ
The following sections show the formal useage syntax for AppWait to start
different types of applications.
For OS/2 or DOS EXE
For OS2 CMD files
For DOS BAT files
For Windows EXE
The general syntax is:
AppWait APP_NAME APP_WORKING_DIRECTORY PARAMETERS_FOR_APP
ΓòÉΓòÉΓòÉ 5.4.1. Useage for OS/2 or DOS EXE ΓòÉΓòÉΓòÉ
AppWait APP_NAME APP_WORKING_DIRECTORY PARAMETERS_FOR_APP
Example (OS/2)
Example (DOS)
ΓòÉΓòÉΓòÉ 5.4.2. Useage for CMD ΓòÉΓòÉΓòÉ
AppWait cmd.exe WORK_DIRECTORY /cCMD_NAME PARAMS_FOR_CMD
Example
ΓòÉΓòÉΓòÉ 5.4.3. Useage for BAT ΓòÉΓòÉΓòÉ
AppWait command.com WORK_DIRECTORY /cBAT_NAME PARAMS_FOR_BAT
Example
ΓòÉΓòÉΓòÉ 5.4.4. Useage for Windows EXE ΓòÉΓòÉΓòÉ
AppWait winos2.com WORK_DIRECTORY APP_NAME PARAMS_FOR_APP
(if this doesn't work on Warp red spine, try win.com instead of winos2.com)
Example
ΓòÉΓòÉΓòÉ 6. Licensing information ΓòÉΓòÉΓòÉ
The trial version of SFUtils may only be used for evaluation purposes and must
be registered for continued use.
You may purchase a personal or site license.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéType ΓöéCost ΓöéDescription Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPersonal Γöé$15 ΓöéFor use on one machine Γöé
Γöélicense Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSite Γöé$150 ΓöéFor use on any number of Γöé
Γöélicense Γöé Γöémachines at one site Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
SFUtils can be purchased through BMT Micro or directly from the author
ΓòÉΓòÉΓòÉ 6.1. Purchase through BMT Micro ΓòÉΓòÉΓòÉ
You can order from BMT Micro using the enclosed purchase applet. It allows you
to fill out your order information and then encrypts it and sends it via the
internet to BMT Micro. It will also print out a form that you can fax or mail.
BMT Micro also has an 800 number for telephone orders. BMT Micro can be
contacted as shown below.
Secure Web Orders: http://www.bmtmicro.com
Mail Orders To: BMT Micro
PO Box 15016
Wilmington, NC 28408
U.S.A.
Voice Orders: 8:00am - 7:00pm EST (-5 GMT)
(800) 414-4268 (orders only)
(910) 791-7052
Fax Orders: (910) 350-2937 24 hours / 7 Days
(800) 346-1672 24 hours / 7 Days
Online Orders via modem: (910) 350-8061 10 lines, all 14.4K
(910) 799-0923 Direct 28.8K line
Ordering and general ordering questions:
Via AOL: bmtmicro
via MSN: bmtmicro
Via Prodigy: HNGP66D
via Compuserve: 74031,307
via Internet: orders@bmtmicro.com
telnet@bmtmicro.com
http://www.bmtmicro.com
We accept Visa, Mastercard, Discover, American Express, Diners
Club, Carte Blanche, Cashiers Check, Personal Check. Personal
checks are subject to clearance. Eurochecks in DM are welcome.
DM, Sterling, and US Currency is welcome but send only by
registered mail, return reciept requested. We cannot be liable
for lost cash sent through the mail.
Purchase orders are welcome, subject to approval. The minimum
amount is $250.00.
Information for our German customers is explained in the last
paragraph of this order form.
Shipping and Handling:
Email - Subject to Credit Card Verification Free
Worldwide 1st Class ....................... Free
2nd Day Priority, USA Only ................ $ 4.00 US
US Postal Service International Express
(Including Canada and Mexico), allow up to
7-10 days ............................... $ 25.00 US
Airborne Select Delivery (USA Only) $ 8.00 US
FedEx Overnight, USA Only (delivery by
3:00 pm the following day) .............. $ 15.00 US
FedEx Europe/Japan (guaranteed delivery
within 3 days) .......................... $ 35.00 US
ORDERING FROM INSIDE GERMANY ONLY
=================================
Persons in Germany wishing to order shareware may also transfer funds
into our account with Deutsche Bank. Once the money is deposited you
may either fax a confirmation to us with proof of deposit or wait until
Deutsche Bank notifies us of the transaction (usually 10-18 business days).
Account information is as follows:
Deutsche Bank / Frankfurt Branch
EmpfДnger: Thomas Bradford / BMT Micro
Konto-Nummer: 0860221
Bankleitzahl: 500-700-10
When you make the transfer, be sure to put your name and the program you
are registering on the transfer.
Current exchange rates can be obtained by sending an email to
dm_to_us@bmtmicro.com. An automated reply will return todays exchange
rates.
It is very important that you send us a completed order form by
either email or fax if you deposit money into this account for a
registration. Fill the order form out as usual except in the credit
card number field put "DEUTSCHE BANK". We will file the order and
use it to match against the deposit information we receive from the
bank.
IMPORTANT!
----------
When you email us your order form, we will reply with an
acknowledgement. If you do not get an acknowledgement within 24 hours
please send your order again in case it was lost. This extra bit of
caution can save a lot of confusion.
If you are concerned that your order is taking too long to process, feel
free to check with us about the status of your order. It's important
to all of us that you feel safe doing business with our company and
please feel free to suggest ways we can improve our service to you.
ΓòÉΓòÉΓòÉ 6.1.1. Purchase applet ΓòÉΓòÉΓòÉ
The purchase applet is purchase.exe included in this distribution.
Instructions, Information, and the obligatory legal requirements
----------------------------------------------------------------
%%%%%%%%%%%%%%%%% DISCLAIMER %%%%%%%%%%%%%%%%%%%
THE USER OF THE PROGRAM BY USING IT AGREES NOT TO HOLD BMT MICRO, INC.
NOR ITS OWNERS NOR ITS EMPLOYEES LIABLE FOR ANY DAMAGE THAT MAY HAVE
BEEN CAUSED BY EITHER THE PROPER OR IMPROPER FUNCTIONING OR BY THE USE
OR MISUSE OF THE PURCHASE APPLET.
%%%%%%%%%%%%%%% END OF DISCLAIMER %%%%%%%%%%%%%%%%%
Tip: If you have an account with BMT Micro, Inc., put your PIN number
==== in the credit card field.
1. The BMT Micro, Inc. purchase applet requires that you be connected
to the internet to submit an online order.
2. Your online order is encrypted prior to being sent. We make no
claims about the ability of another party to intercept and decipher
your online order. In fact, the chances of an online order being
intercepted is exactly the same as any other email message you send.
The encryption routine does provide an extra layer of security. I
personally would have no problem using this application to send an
order but if you are really, really concerned about security please
use our secure web server to place an order at http:\\www.bmtmicro.com.
3. When you send an order the program also creates a text file named
register.frm. Please print this and save it as a record of your
order.
4. If you wish to pay by means other than a credit card the program
will print an order form suitable for mailing. The printed order
form has our mailing address.
5. The pricing of the products in the list is current as of
April 29, 1997. If for any reason there is a price difference
between the current price and the listed price we will contact you
via email prior to processing the order. Under no circumstances
will we bill you any amount higher than is quoted on the order form.
6. BMT Micro, Inc. makes no claims for this purchase applet. If you
place an online order and do not hear from us within 24 hours please
contact us at bmt@bmtmicro.com and we'll check it out. You can
expect to hear from us even in the case of declined credit cards or
orders that cannot be processed for any reason.
ΓòÉΓòÉΓòÉ 6.2. Purchase through author ΓòÉΓòÉΓòÉ
You may order SFUtils directly from the author:
Darren V. Croft
PO Box 711706
Salt Lake City, UT 84171
Send a check in US funds
Specify email or postal delivery.
Include email address for update notification.
( email dvc@ibm.net with questions )
ΓòÉΓòÉΓòÉ 7. Tech support ΓòÉΓòÉΓòÉ
All support is handled by the author either via email or postal mail.
BMT Micro does not handle tech support.
Please contact:
dvc@ibm.net
Darren Croft
PO Box 711706
Salt Lake City, UT 84171